Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: move one or more collaborators to emeritus #56580

Merged
merged 1 commit into from
Jan 27, 2025

Conversation

nodejs-github-bot
Copy link
Collaborator

This PR was generated by the find-inactive-collaborators.yml workflow.

@nodejs/tsc Please follow up with the offboarding tasks.

@nodejs-github-bot nodejs-github-bot added meta Issues and PRs related to the general management of the project. doc Issues and PRs related to the documentations. labels Jan 13, 2025
@targos
Copy link
Member

targos commented Jan 13, 2025

Anatoli is still a TSC regular member, hence the linter error.

@aduh95
Copy link
Contributor

aduh95 commented Jan 13, 2025

/cc @apapirovski FYI

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mhdawson
Copy link
Member

@targos I think when a collaborator drops out due to inactivity they move from regular to emeritus for the TSC, right? If so I'm happy to open a PR which will do that move.

@mhdawson
Copy link
Member

Just going to see if I can give Anatoli a heads up through email and then will open the PR to move him to emeritus, that should resolve the linter issue.

@mhdawson
Copy link
Member

PR to move Anatoli to emeritus - #56592

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Thanks!

@aduh95 aduh95 force-pushed the actions/inactive-collaborators branch from cd71cc9 to 7ce3b50 Compare January 27, 2025 22:06
@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. labels Jan 27, 2025
@mhdawson
Copy link
Member

I don't see a way to rebase this so that the linter passes (which it should since #56592 landed).

Unless somebody has a better suggestion by tomorrow I'll close this PR and re-run the action to get a new PR we can land.

aduh95 added a commit to nodejs/create-node-meeting-artifacts that referenced this pull request Jan 27, 2025
mhdawson pushed a commit to nodejs/create-node-meeting-artifacts that referenced this pull request Jan 27, 2025
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Jan 27, 2025
@nodejs-github-bot nodejs-github-bot merged commit 532fff6 into main Jan 27, 2025
20 checks passed
@nodejs-github-bot
Copy link
Collaborator Author

Landed in 532fff6

@nodejs-github-bot nodejs-github-bot deleted the actions/inactive-collaborators branch January 27, 2025 22:15
aduh95 pushed a commit that referenced this pull request Jan 27, 2025
PR-URL: #56580
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Ulises Gascón <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Rafael Gonzaga <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. doc Issues and PRs related to the documentations. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.